Release 10.1A: OpenEdge Development:
Web Services

Programming for session-managed Web services

The programming model for session-managed Web services is similar to programming all other Open Clients, except for the use of object IDs:

Before invoking any other method on a session-managed AppObject, you must instantiate (create) and call a connect method on the object to establish a connection to the AppServer context. The client must obtain the object ID for the AppObject after it is created. After that, you can invoke any method on the AppObject. Calls to all AppObject methods are sequential (calls follow one another) using the established connection. You must call the release method on an AppObject when you no longer need the object (Web service).
You can create ProcObjects and SubAppObjects using class factory methods on the AppObject or create ProcObjects on another SubAppObject. Once created, all objects share the same connection. This connection terminates only after you have called the release method on all Web service objects that you create. You must call each object's release method when you no longer need the object.
You can call methods on a ProcObject as soon as you create it and after the client obtains the object ID for it. Calls to all ProcObject methods (internal procedures and user-defined functions) are sequential using the connection established by the AppObject. You must call the release method on a ProcObject when you no longer need the object.
You can call methods on a SubAppObject as soon as you create it and after the client obtains the object ID for it. Calls to all SubAppObject methods are sequential using the connection established for the AppObject. You must call the release method on a SubAppObject when you no longer need the object.
Once connected to a session-managed Web service, you must always send object IDs with each method call.